1001 Secrets for Windows NT Registry
(Publisher: 29th Street Press)
Author(s): Tim Daniels
ISBN: 1882419685
Publication Date: 12/01/97

Previous Table of Contents Next


This value identifies the full virtual path to the error page returned in response to errors in the .idq file. The CiRestriction, CiErrorMessage, and CiErrorNumber variables can all be referenced in the .htx file.

III-111 Value Name: ISAPIRestrictionErrorFile
Data Type: REG_SZ
Value: /Scripts/Samples/Search/ResError.htx

This value identifies the full virtual path to the error page returned in response to errors in the query restriction (CiRestriction). This is the error page that users see most often. The CiRestriction, CiErrorMessage, and CiErrorNumber variables can all be referenced in the .htx file.

III-112 Value Name: Locale
Data Type: REG_DWORD
Value: 0x409

This value associates the registry section with a specific locale.

III-113 Value Name: NoiseFile
Data Type: REG_SZ
Value: noise.enu

This value identifies the file name of the noise-word list for this locale. The file must be located in the %SystemRoot%\System32 directory.

III-114 Value Name: StemmerClass
Data Type: REG_SZ
Value: {eeed4c20-7f1b-11ce-be57-00aa0051fe20}

This value identifies the ActiveX class ID of the class used for locale-specific stemming.

III-115 Value Name: WbreakerClass
Data Type: REG_SZ
Value: {59E09780-8099-101B-8DF3-00000B65C3B5}

This value identifies the ActiveX class ID of the class used to split phrases for this locale.

III-116 If Microsoft Index Server is currently indexing all your files, you can make it quit by limiting Index Server to indexing just those files you register.

Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Control\ContentIndex
Value Name: FilterFilesWithUnknownExtensions
Data Type: REG_DWORD
Value: 0

A value of 0 tells the Content indexer to Index only those file types that have been registered and ignore the rest. This feature is handy when you don’t want to index .exe files and .com files, for example.

SQL Server

III-117 You can specify the protocol you want SQL Executive to use in its Advanced tab, but if you need to specify a particular protocol for SQL Executive to use when connecting to servers, you need to add the following registry entry.

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\MSSQLServer\SQLExecutive\
Value Name: ServerHost
Data Type: REG_SZ
Value: < server >

You must still create a specific server connection in the Advanced tab of the SQL Client Configuration Utility. Then set the ServerHost value in the SQL Executive section of the registry to the appropriate server name. SQL should then use the defined protocol on all its connection attempts to subscribing servers.

III-118 To increase the concurrent number of SQLExec tasks that use a DB-Library connection, change the following registry value.

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\MSSQLServer\SQLExecutive
Value Name: MaxDBProcesses
Data Type: REG_DWORD
Value: 61

The number of available concurrent tasks is the number of MaxDBProcesses — three for SQL overhead. Restart your SQL server for these changes to take effect.

III-119 If the SQLMonitor Service on Windows NT won’t start and you recently changed the SQL Server SA accounts password, you should change it back. If you can’t remember the password, here’s how to fix the problem.

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\SQLServer\SQLMONITOR\Parameters
Value Name: Password
Data Type: REG_SZ

Type the new SA account password for the value.

Value: password

Restart the machine for these changes to take effect.

III-120 You’ve installed SQL Server 6.5, but SQL Executive does not come up. When you try to start it from the Control Panel, you get an Error 109. To fix the problem, change this registry value.

Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\SQLServer\CurrentVersion
Value Name: CurrentVersion
Data Type: REG_SZ
Value: 6.50.201

Restart the machine for these changes to take effect.


Previous Table of Contents Next